Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9804f11fbaa382a50a01282dfb3341d0a0d39000fa24335437d325b204e07159

Tx prefix hash: baaa0418433197310f2c40636c44ccc5b205a4dbd0be9f0ce1d65ee8a95faf73
Tx public key: 4ce0468dc448960c5ab2f8e433b0c68acc6a8ddc5f18b9f992632dd6ac929012
Timestamp: 1714539864 Timestamp [UCT]: 2024-05-01 05:04:24 Age [y:d:h:m:s]: 01:030:07:24:55
Block: 1012292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282626 RingCT/type: yes/0
Extra: 014ce0468dc448960c5ab2f8e433b0c68acc6a8ddc5f18b9f992632dd6ac9290120211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 434cefabfac70863e7f0e7a86a9580e322f800510fc01e8c574ffc25e6f561c9 0.600000000000 1474772 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": 1012302, "vin": [ { "gen": { "height": 1012292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "434cefabfac70863e7f0e7a86a9580e322f800510fc01e8c574ffc25e6f561c9" } } ], "extra": [ 1, 76, 224, 70, 141, 196, 72, 150, 12, 90, 178, 248, 228, 51, 176, 198, 138, 204, 106, 141, 220, 95, 24, 185, 249, 146, 99, 45, 214, 172, 146, 144, 18, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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