Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2cde7d275995f853bf9e80850c73346111d534b2b93029d57b1a5c75e8b3a15

Tx prefix hash: 0da0a6a0cd12388da7f3810550129a7cc6adffdb50c3185df69f28fe649a8c1f
Tx public key: 0eecf7f08d4f8cbad6d5912d4a2c0a5040870960dd0519c608aa706f00f7f680
Timestamp: 1733579779 Timestamp [UCT]: 2024-12-07 13:56:19 Age [y:d:h:m:s]: 00:102:21:52:36
Block: 1170037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73367 RingCT/type: yes/0
Extra: 010eecf7f08d4f8cbad6d5912d4a2c0a5040870960dd0519c608aa706f00f7f680021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f634a6e9f39524c8500a29e9b7d0ba8f7ea85d29f8f8c6fbf9126cb6957aa30 0.600000000000 1655766 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": 1170047, "vin": [ { "gen": { "height": 1170037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f634a6e9f39524c8500a29e9b7d0ba8f7ea85d29f8f8c6fbf9126cb6957aa30" } } ], "extra": [ 1, 14, 236, 247, 240, 141, 79, 140, 186, 214, 213, 145, 45, 74, 44, 10, 80, 64, 135, 9, 96, 221, 5, 25, 198, 8, 170, 112, 111, 0, 247, 246, 128, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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