Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bb8f564659df766df722ab6f575945a479559730f31f5cfb901870c8970804b

Tx prefix hash: 0feb744c1834dee512a2cf56663ea5a652a45a3c3c63fdd29e6a94ef959505f7
Tx public key: 76603b9ca54de7b7d3188a9aabb7d50c613aafeaa349daa7103f3e99970982c2
Timestamp: 1734659067 Timestamp [UCT]: 2024-12-20 01:44:27 Age [y:d:h:m:s]: 00:104:01:51:29
Block: 1178994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74137 RingCT/type: yes/0
Extra: 0176603b9ca54de7b7d3188a9aabb7d50c613aafeaa349daa7103f3e99970982c20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a7755bbd4c39a0bcb9da7b1d7f8895565da89dbc1e84d1077de4fbb56c224c7 0.600000000000 1665385 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": 1179004, "vin": [ { "gen": { "height": 1178994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a7755bbd4c39a0bcb9da7b1d7f8895565da89dbc1e84d1077de4fbb56c224c7" } } ], "extra": [ 1, 118, 96, 59, 156, 165, 77, 231, 183, 211, 24, 138, 154, 171, 183, 213, 12, 97, 58, 175, 234, 163, 73, 218, 167, 16, 63, 62, 153, 151, 9, 130, 194, 2, 17, 0, 0, 0, 3, 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