Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdbf3f6bddd0b8e0b79f17d894fa8ae763486abc7bbec5fd2b6ce65ea278e3a3

Tx prefix hash: e631de0db62c801d764b1b6d93367170a4cab03b89c45ca5b06498cd0b1561c2
Tx public key: 317ee560176f38543eb82a2429778a2013f84ec111f2cebc5c6f2de828db422f
Timestamp: 1701720309 Timestamp [UCT]: 2023-12-04 20:05:09 Age [y:d:h:m:s]: 01:122:14:30:46
Block: 906007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348777 RingCT/type: yes/0
Extra: 01317ee560176f38543eb82a2429778a2013f84ec111f2cebc5c6f2de828db422f021100000001e08532b6000000000000000000

1 output(s) for total of 0.610973934000 dcy

stealth address amount amount idx
00: fe7356933c425c99eb3b0771c9c42320f62d9f9ab90e162fd2cd08bfe37ce5a4 0.610973934000 1362928 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": 906017, "vin": [ { "gen": { "height": 906007 } } ], "vout": [ { "amount": 610973934, "target": { "key": "fe7356933c425c99eb3b0771c9c42320f62d9f9ab90e162fd2cd08bfe37ce5a4" } } ], "extra": [ 1, 49, 126, 229, 96, 23, 111, 56, 84, 62, 184, 42, 36, 41, 119, 138, 32, 19, 248, 78, 193, 17, 242, 206, 188, 92, 111, 45, 232, 40, 219, 66, 47, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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