Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 314d5494e98855c38a49304803822d4d5544b653dd615c78738d26d609f97a3a

Tx prefix hash: 84500d48a8b6927685291b91149743f38782fa2164c14a1aaa2bc58619d130a4
Tx public key: a30d7be54a111b89c77be3fef9d0b74c7952bae8b0d96e746b77baf2822a5b24
Timestamp: 1725992911 Timestamp [UCT]: 2024-09-10 18:28:31 Age [y:d:h:m:s]: 00:122:11:45:48
Block: 1107240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87607 RingCT/type: yes/0
Extra: 01a30d7be54a111b89c77be3fef9d0b74c7952bae8b0d96e746b77baf2822a5b24021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3853fc984d4a9dd7bf5990edfb9c69499a72cd853912aae831e91602ea98b474 0.600000000000 1584849 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": 1107250, "vin": [ { "gen": { "height": 1107240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3853fc984d4a9dd7bf5990edfb9c69499a72cd853912aae831e91602ea98b474" } } ], "extra": [ 1, 163, 13, 123, 229, 74, 17, 27, 137, 199, 123, 227, 254, 249, 208, 183, 76, 121, 82, 186, 232, 176, 217, 110, 116, 107, 119, 186, 242, 130, 42, 91, 36, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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