Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3317008a04f0a47e23f1a9071e31861fd1ef753beb13508984f4c3547ae9a2e0

Tx prefix hash: a99b783d2c46d058cdede739bbcd27216cd4778da972aab49f999613ec504430
Tx public key: ffc0bae2c75510c7df1d7daa0d0297d03307d704634c100be5a580fd0b0c8de0
Timestamp: 1700563691 Timestamp [UCT]: 2023-11-21 10:48:11 Age [y:d:h:m:s]: 01:167:23:29:14
Block: 896413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381250 RingCT/type: yes/0
Extra: 01ffc0bae2c75510c7df1d7daa0d0297d03307d704634c100be5a580fd0b0c8de002110000000c33af99f4000000000000000000

1 output(s) for total of 0.657372604000 dcy

stealth address amount amount idx
00: 388c2a7a155d099d5e6c5a0baa4464fa45932d83d572b22eb47aae1eb4343696 0.657372604000 1352718 of 0

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": 896423, "vin": [ { "gen": { "height": 896413 } } ], "vout": [ { "amount": 657372604, "target": { "key": "388c2a7a155d099d5e6c5a0baa4464fa45932d83d572b22eb47aae1eb4343696" } } ], "extra": [ 1, 255, 192, 186, 226, 199, 85, 16, 199, 223, 29, 125, 170, 13, 2, 151, 208, 51, 7, 215, 4, 99, 76, 16, 11, 229, 165, 128, 253, 11, 12, 141, 224, 2, 17, 0, 0, 0, 12, 51, 175, 153, 244, 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