Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f381245332f55d85d0e0741335acbd90815c2e809a46c35aaa509796b35efc5

Tx prefix hash: 62e9068b268655f83b786bf2d970bba83b5f7a015971de643af7a85a680f240e
Tx public key: 811972f975ae7ff8ebc02cef925afb1a908d7bb3221e1f79e9577c8d951d7ad1
Timestamp: 1731083646 Timestamp [UCT]: 2024-11-08 16:34:06 Age [y:d:h:m:s]: 00:128:19:36:11
Block: 1149364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91900 RingCT/type: yes/0
Extra: 01811972f975ae7ff8ebc02cef925afb1a908d7bb3221e1f79e9577c8d951d7ad1021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ef94dbb948d332a185e1a55fc5e1ef17e6d9272085a476ad72d7c792198218f 0.600000000000 1634427 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": 1149374, "vin": [ { "gen": { "height": 1149364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ef94dbb948d332a185e1a55fc5e1ef17e6d9272085a476ad72d7c792198218f" } } ], "extra": [ 1, 129, 25, 114, 249, 117, 174, 127, 248, 235, 192, 44, 239, 146, 90, 251, 26, 144, 141, 123, 179, 34, 30, 31, 121, 233, 87, 124, 141, 149, 29, 122, 209, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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