Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ec79f9af9a969872a25f84558e524986018d6b73f19ffa1b9fb40d304fd3670

Tx prefix hash: d530265a3f104aa78f4f8777d93927a46c9df08f60bed2773531e09f6c3af6e7
Tx public key: bba59f45b739990a612aae4195fc2cd3dc85bc79f43c13be6a2d995548cf6c60
Timestamp: 1735505534 Timestamp [UCT]: 2024-12-29 20:52:14 Age [y:d:h:m:s]: 00:132:16:07:48
Block: 1185971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94635 RingCT/type: yes/0
Extra: 01bba59f45b739990a612aae4195fc2cd3dc85bc79f43c13be6a2d995548cf6c600211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fd55c29a53d077931a738bbe9a47fa4e4fdc039db8d42f0924a88c00ac69c07 0.600000000000 1672446 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": 1185981, "vin": [ { "gen": { "height": 1185971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fd55c29a53d077931a738bbe9a47fa4e4fdc039db8d42f0924a88c00ac69c07" } } ], "extra": [ 1, 187, 165, 159, 69, 183, 57, 153, 10, 97, 42, 174, 65, 149, 252, 44, 211, 220, 133, 188, 121, 244, 60, 19, 190, 106, 45, 153, 85, 72, 207, 108, 96, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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