Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f409bd8071e4a8b659c96cdaa1f229e5481460ae6e7b84963cd3d2e162b0090

Tx prefix hash: 1d568c941cd84048986a52f62c399505719b34beca0d3a1baf55faa68e8491c3
Tx public key: 40bbc55731d964c21be6e933ca6da72d994fe1c427025aaa61c28221a96af5bc
Timestamp: 1734858960 Timestamp [UCT]: 2024-12-22 09:16:00 Age [y:d:h:m:s]: 00:177:11:55:47
Block: 1180654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126537 RingCT/type: yes/0
Extra: 0140bbc55731d964c21be6e933ca6da72d994fe1c427025aaa61c28221a96af5bc0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4f48bf80cfd49f06cf9b93e634c380c2dde6e5a5d4b8a47b0a59adeb4ddd396 0.600000000000 1667067 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": 1180664, "vin": [ { "gen": { "height": 1180654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f48bf80cfd49f06cf9b93e634c380c2dde6e5a5d4b8a47b0a59adeb4ddd396" } } ], "extra": [ 1, 64, 187, 197, 87, 49, 217, 100, 194, 27, 230, 233, 51, 202, 109, 167, 45, 153, 79, 225, 196, 39, 2, 90, 170, 97, 194, 130, 33, 169, 106, 245, 188, 2, 17, 0, 0, 0, 7, 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