Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fedb1f9d55949fe561d8f026091aad21dc81231dd7fced181b75d8c7afe36a3

Tx prefix hash: 37ab74b688ffb0ad6c6c2438deac2960bf7d0047680426fbc7df75ad7fd0bcdf
Tx public key: cc84a19957354ac8731d7800d10612a3e01f2f9ff1dcfa2629ebffeaa5dc23d7
Timestamp: 1681629796 Timestamp [UCT]: 2023-04-16 07:23:16 Age [y:d:h:m:s]: 01:271:21:52:29
Block: 739686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455833 RingCT/type: yes/0
Extra: 01cc84a19957354ac8731d7800d10612a3e01f2f9ff1dcfa2629ebffeaa5dc23d70211000000085029cbac000000000000000000

1 output(s) for total of 2.173268784000 dcy

stealth address amount amount idx
00: a6c8a6a2aada45f24c19192a9e066cfb13cb68115269ef0539f823392dffb5b2 2.173268784000 1186549 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": 739696, "vin": [ { "gen": { "height": 739686 } } ], "vout": [ { "amount": 2173268784, "target": { "key": "a6c8a6a2aada45f24c19192a9e066cfb13cb68115269ef0539f823392dffb5b2" } } ], "extra": [ 1, 204, 132, 161, 153, 87, 53, 74, 200, 115, 29, 120, 0, 209, 6, 18, 163, 224, 31, 47, 159, 241, 220, 250, 38, 41, 235, 255, 234, 165, 220, 35, 215, 2, 17, 0, 0, 0, 8, 80, 41, 203, 172, 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