Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f3de387d2e33028f6d30504882e74e41638a226d36904c44874768f5b2db647

Tx prefix hash: 3d0ca20c57c6454d04606c3c5c9b13175abe8aac989cfca55f92f80db339b06e
Tx public key: 0b8c4ae3701bbfdabecb2c3c44421236e48ad6bc1f53b039fc938d1ccbb161df
Timestamp: 1712422435 Timestamp [UCT]: 2024-04-06 16:53:55 Age [y:d:h:m:s]: 01:003:13:53:14
Block: 994703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263547 RingCT/type: yes/0
Extra: 010b8c4ae3701bbfdabecb2c3c44421236e48ad6bc1f53b039fc938d1ccbb161df02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b675f59a06b3a83aec424c6ee6655fccc7cb9cf076672312f8a9c9612c3be32 0.600000000000 1455107 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": 994713, "vin": [ { "gen": { "height": 994703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b675f59a06b3a83aec424c6ee6655fccc7cb9cf076672312f8a9c9612c3be32" } } ], "extra": [ 1, 11, 140, 74, 227, 112, 27, 191, 218, 190, 203, 44, 60, 68, 66, 18, 54, 228, 138, 214, 188, 31, 83, 176, 57, 252, 147, 141, 28, 203, 177, 97, 223, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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