Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ebdc359bacc2df4b0a4b83155b4a6c45d235a281ec94e54b60506c6e72bc1d6

Tx prefix hash: 6458fa3aa0f3151557b6410ce5b2c3575b1a790147d0278b2e01257713e32b2e
Tx public key: b07937879900b26c77fcd62e49d197b9e60e22357bc79cb4aa48c46188b80146
Timestamp: 1723590536 Timestamp [UCT]: 2024-08-13 23:08:56 Age [y:d:h:m:s]: 01:056:12:52:55
Block: 1087317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298828 RingCT/type: yes/0
Extra: 01b07937879900b26c77fcd62e49d197b9e60e22357bc79cb4aa48c46188b80146021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f8c09d7df36a94ae84a1e1de9416cee66952f446ebec83ac56b2eef912bb980 0.600000000000 1561924 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": 1087327, "vin": [ { "gen": { "height": 1087317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f8c09d7df36a94ae84a1e1de9416cee66952f446ebec83ac56b2eef912bb980" } } ], "extra": [ 1, 176, 121, 55, 135, 153, 0, 178, 108, 119, 252, 214, 46, 73, 209, 151, 185, 230, 14, 34, 53, 123, 199, 156, 180, 170, 72, 196, 97, 136, 184, 1, 70, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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