Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90746e077b2ac9fcb23f663954883945dce1e183ba37373c924e109731fb5f8a

Tx prefix hash: ee6dd1d9b19487a720b116183d56b7614158bac3eb127aa0a89e3dba32bfe37a
Tx public key: 888507fa3a10b7ea0534d45e1667fe3a416fef2a88cc729a583c324f76488184
Timestamp: 1730569637 Timestamp [UCT]: 2024-11-02 17:47:17 Age [y:d:h:m:s]: 00:197:02:12:02
Block: 1145097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140721 RingCT/type: yes/0
Extra: 01888507fa3a10b7ea0534d45e1667fe3a416fef2a88cc729a583c324f76488184021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4b7ff13e4d4cda32f841d143070e694546d4538314011f104b4ef96b0f26f15 0.600000000000 1629476 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": 1145107, "vin": [ { "gen": { "height": 1145097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4b7ff13e4d4cda32f841d143070e694546d4538314011f104b4ef96b0f26f15" } } ], "extra": [ 1, 136, 133, 7, 250, 58, 16, 183, 234, 5, 52, 212, 94, 22, 103, 254, 58, 65, 111, 239, 42, 136, 204, 114, 154, 88, 60, 50, 79, 118, 72, 129, 132, 2, 17, 0, 0, 0, 4, 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