Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f2864601347ece2b588429b3ed3f55c68735a356f297244258f39faaa352531

Tx prefix hash: a7ad182e5e564d7cef3ef1e301d37650f969964e8a6f95d9c90b54a6de7f4525
Tx public key: 26983b8995eed986fb5ce586edb7e99f823df2228cbf17e492b1e36382aa0d82
Timestamp: 1732222349 Timestamp [UCT]: 2024-11-21 20:52:29 Age [y:d:h:m:s]: 00:206:14:42:40
Block: 1158788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147421 RingCT/type: yes/0
Extra: 0126983b8995eed986fb5ce586edb7e99f823df2228cbf17e492b1e36382aa0d82021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7b0c143c365e7dec4bf85f0c0b8655c21f52e79f579f44df4ad09e3a09dbe9a 0.600000000000 1644417 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": 1158798, "vin": [ { "gen": { "height": 1158788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7b0c143c365e7dec4bf85f0c0b8655c21f52e79f579f44df4ad09e3a09dbe9a" } } ], "extra": [ 1, 38, 152, 59, 137, 149, 238, 217, 134, 251, 92, 229, 134, 237, 183, 233, 159, 130, 61, 242, 34, 140, 191, 23, 228, 146, 177, 227, 99, 130, 170, 13, 130, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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