Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 430c8430e3f3f4fb4d2d07f05684588e0f24734250a15c94dd069734adf0ace1

Tx prefix hash: c4a404fb5e366f5dba027a24301e370a0bdf015ef3ee1826400828d755dbb525
Tx public key: 75db14d7c00123b4f09d45d7743ee7c002930c3973c977f2833c8b87da4ae813
Timestamp: 1702367154 Timestamp [UCT]: 2023-12-12 07:45:54 Age [y:d:h:m:s]: 01:120:03:06:40
Block: 911381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346988 RingCT/type: yes/0
Extra: 0175db14d7c00123b4f09d45d7743ee7c002930c3973c977f2833c8b87da4ae813021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 149cfa1fec3b9980e95c3a75bf550a3f73cdcb9d7059b79779963f0b7b15ad06 0.600000000000 1368581 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": 911391, "vin": [ { "gen": { "height": 911381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "149cfa1fec3b9980e95c3a75bf550a3f73cdcb9d7059b79779963f0b7b15ad06" } } ], "extra": [ 1, 117, 219, 20, 215, 192, 1, 35, 180, 240, 157, 69, 215, 116, 62, 231, 192, 2, 147, 12, 57, 115, 201, 119, 242, 131, 60, 139, 135, 218, 74, 232, 19, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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