Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2411b134dbd3abd22709f50bb01279bb2d4e4e068f6212938020f6a33d277569

Tx prefix hash: 0d5dd15d563cd6734cbba9a1e75af9e99a5dcf0cc3cb3a51b08e540300a15b1c
Tx public key: 4bceaa4ee497a13b564818e84ce5c3f43743e9029296c5944a8eaaa4d0e419b4
Timestamp: 1731457107 Timestamp [UCT]: 2024-11-13 00:18:27 Age [y:d:h:m:s]: 00:011:10:51:10
Block: 1152436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8207 RingCT/type: yes/0
Extra: 014bceaa4ee497a13b564818e84ce5c3f43743e9029296c5944a8eaaa4d0e419b40211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78763cce97ae5b08250274fc0fbd6109f7a84ebd8628f6bad5fe5d8133b4852d 0.600000000000 1638033 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": 1152446, "vin": [ { "gen": { "height": 1152436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78763cce97ae5b08250274fc0fbd6109f7a84ebd8628f6bad5fe5d8133b4852d" } } ], "extra": [ 1, 75, 206, 170, 78, 228, 151, 161, 59, 86, 72, 24, 232, 76, 229, 195, 244, 55, 67, 233, 2, 146, 150, 197, 148, 74, 142, 170, 164, 208, 228, 25, 180, 2, 17, 0, 0, 0, 6, 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