Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f6281d32736466fd06d1ac8196a77b5d33700ab62f531bc24df034a16328015

Tx prefix hash: d7328fe64e905ff2409f6c2e0fd4aed87bc926979a3bfceac1766caea7c70e41
Tx public key: ae892cef88afde0779240175252a3b9a2bde8c30076b1bc592dd986b7f4b5297
Timestamp: 1712912711 Timestamp [UCT]: 2024-04-12 09:05:11 Age [y:d:h:m:s]: 01:035:08:41:31
Block: 998779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286262 RingCT/type: yes/0
Extra: 01ae892cef88afde0779240175252a3b9a2bde8c30076b1bc592dd986b7f4b529702110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 424ca1ae518ea1b292c6004d2dbe53b6ebcf3b55285263a5aea0bfc74c5da23b 0.600000000000 1459237 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": 998789, "vin": [ { "gen": { "height": 998779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "424ca1ae518ea1b292c6004d2dbe53b6ebcf3b55285263a5aea0bfc74c5da23b" } } ], "extra": [ 1, 174, 137, 44, 239, 136, 175, 222, 7, 121, 36, 1, 117, 37, 42, 59, 154, 43, 222, 140, 48, 7, 107, 27, 197, 146, 221, 152, 107, 127, 75, 82, 151, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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