Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f14bc726121761af0d405525f5ac552cffabd4a49194e111e314aaf37ff742d

Tx prefix hash: 32e9b3ae8c91076a7b8ea11726f3c5655f1099dd4f6db4ea1b57beaed1affbba
Tx public key: b0e9a6c333057dcd47a109131667c135a3ef22b421139030b15ea3a68d73f94e
Timestamp: 1721442587 Timestamp [UCT]: 2024-07-20 02:29:47 Age [y:d:h:m:s]: 00:301:05:23:35
Block: 1069557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215191 RingCT/type: yes/0
Extra: 01b0e9a6c333057dcd47a109131667c135a3ef22b421139030b15ea3a68d73f94e021100000002162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8fc7cc810416a263ff0341d2d845d9cff7133271e9339ca64b92a2741d047d5 0.600000000000 1541018 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": 1069567, "vin": [ { "gen": { "height": 1069557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8fc7cc810416a263ff0341d2d845d9cff7133271e9339ca64b92a2741d047d5" } } ], "extra": [ 1, 176, 233, 166, 195, 51, 5, 125, 205, 71, 161, 9, 19, 22, 103, 193, 53, 163, 239, 34, 180, 33, 19, 144, 48, 177, 94, 163, 166, 141, 115, 249, 78, 2, 17, 0, 0, 0, 2, 22, 38, 19, 170, 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