Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38b8c9ff273101fe56cc916698e5061c4993f9612aad5edb70f4d55e7e52b55d

Tx prefix hash: 15354dbdf91c348ade0048efa66b1dfd670e5ff2d25e6085c552cb03d3e9306a
Tx public key: 671df9c19b724e22dd118c38f670c914862cb27ddbd24a5eb01ac726ca4d1a5c
Timestamp: 1648903882 Timestamp [UCT]: 2022-04-02 12:51:22 Age [y:d:h:m:s]: 03:213:06:21:54
Block: 471642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 930486 RingCT/type: yes/0
Extra: 01671df9c19b724e22dd118c38f670c914862cb27ddbd24a5eb01ac726ca4d1a5c02110000000a2e6b1fd5000000000000000000

1 output(s) for total of 16.797881497000 dcy

stealth address amount amount idx
00: bb2d67871de68825e1246c5b2975dac870d9590c1273180ef07f014649286ba3 16.797881497000 891016 of 0

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": 471652, "vin": [ { "gen": { "height": 471642 } } ], "vout": [ { "amount": 16797881497, "target": { "key": "bb2d67871de68825e1246c5b2975dac870d9590c1273180ef07f014649286ba3" } } ], "extra": [ 1, 103, 29, 249, 193, 155, 114, 78, 34, 221, 17, 140, 56, 246, 112, 201, 20, 134, 44, 178, 125, 219, 210, 74, 94, 176, 26, 199, 38, 202, 77, 26, 92, 2, 17, 0, 0, 0, 10, 46, 107, 31, 213, 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