Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f676b30ed1ba4d453c013fc17da0b55bd7a4e6d48be1a1aa144fcfebc405ddd

Tx prefix hash: d216c79dfccce5699e31988c571e32eeacbf540c9fdd1e4ce855748dbed9a775
Tx public key: 767aae045317c796ec28273bb4215d364b12b4362b428b661d58430f1fa0abc3
Timestamp: 1700572203 Timestamp [UCT]: 2023-11-21 13:10:03 Age [y:d:h:m:s]: 01:098:01:56:35
Block: 896485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331243 RingCT/type: yes/0
Extra: 01767aae045317c796ec28273bb4215d364b12b4362b428b661d58430f1fa0abc302110000000233af99f4000000000000000000

1 output(s) for total of 0.657011596000 dcy

stealth address amount amount idx
00: 9c6469ceaf43faa6de1e69e3e9a1f0a933116ed79e8a41c2b48e19976aaaf682 0.657011596000 1352796 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": 896495, "vin": [ { "gen": { "height": 896485 } } ], "vout": [ { "amount": 657011596, "target": { "key": "9c6469ceaf43faa6de1e69e3e9a1f0a933116ed79e8a41c2b48e19976aaaf682" } } ], "extra": [ 1, 118, 122, 174, 4, 83, 23, 199, 150, 236, 40, 39, 59, 180, 33, 93, 54, 75, 18, 180, 54, 43, 66, 139, 102, 29, 88, 67, 15, 31, 160, 171, 195, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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