Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 60798f03814f79a5a72b7c7e262afab43da29d402ddf8588c41f3f4bf80e2862

Tx prefix hash: 733c2c32e127526987f83e995ebe58dad4be58e1419d8b1a6bf10c0e83b4bc1d
Tx public key: a29452059b7cb5d12cbf48a0049c141cf315f48cf8496ea60a3a3ffe60f9319c
Timestamp: 1719639861 Timestamp [UCT]: 2024-06-29 05:44:21 Age [y:d:h:m:s]: 00:177:08:37:40
Block: 1054571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126950 RingCT/type: yes/0
Extra: 01a29452059b7cb5d12cbf48a0049c141cf315f48cf8496ea60a3a3ffe60f9319c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6610a71e9c690bc039fbf1df0ba0a4ad1e3d1e3892a28facbc15099ed202a024 0.600000000000 1524934 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1054581, "vin": [ { "gen": { "height": 1054571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6610a71e9c690bc039fbf1df0ba0a4ad1e3d1e3892a28facbc15099ed202a024" } } ], "extra": [ 1, 162, 148, 82, 5, 155, 124, 181, 209, 44, 191, 72, 160, 4, 156, 20, 28, 243, 21, 244, 140, 248, 73, 110, 166, 10, 58, 63, 254, 96, 249, 49, 156, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8