Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b32c261234d0fab660af1eeb183d7747435c87ec15346ae1bbc276b521cb3b2

Tx prefix hash: 34303fb5c182227c0ff6acf3e672f1972200e35670aefba1f413930ade855c90
Tx public key: e1e83bbdcd2d29589e2de3a8e1fc3c5ab2e3111a91d78cb7937bc6ea92f5dd98
Timestamp: 1706442257 Timestamp [UCT]: 2024-01-28 11:44:17 Age [y:d:h:m:s]: 01:147:21:50:13
Block: 945127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366601 RingCT/type: yes/0
Extra: 01e1e83bbdcd2d29589e2de3a8e1fc3c5ab2e3111a91d78cb7937bc6ea92f5dd9802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aac4121ca76581567ca96ec66146244d7e68d3492c1c2f4ef30d6211b4a17fd 0.600000000000 1403437 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": 945137, "vin": [ { "gen": { "height": 945127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aac4121ca76581567ca96ec66146244d7e68d3492c1c2f4ef30d6211b4a17fd" } } ], "extra": [ 1, 225, 232, 59, 189, 205, 45, 41, 88, 158, 45, 227, 168, 225, 252, 60, 90, 178, 227, 17, 26, 145, 215, 140, 183, 147, 123, 198, 234, 146, 245, 221, 152, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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