Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a71b31648fb95b3c5fc9c65c43e36dd77c055b1286f6df2ec64cbf71350986e3

Tx prefix hash: 59bd98598def316b7cf4a9e20d667ac79fd57ef986ab4a5dd8cd31fca159f9fb
Tx public key: 62bd7378cba1bd2bbd4b284016c4a78523f88a448b6ebec24561cb38b72461b6
Timestamp: 1702165197 Timestamp [UCT]: 2023-12-09 23:39:57 Age [y:d:h:m:s]: 01:157:09:43:08
Block: 909703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373656 RingCT/type: yes/0
Extra: 0162bd7378cba1bd2bbd4b284016c4a78523f88a448b6ebec24561cb38b72461b6021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afdbf6aa3641e87dcfdfdae076515ed6ab485a8ce58a2d8cb6a4f55fd573f9c0 0.600000000000 1366808 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": 909713, "vin": [ { "gen": { "height": 909703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afdbf6aa3641e87dcfdfdae076515ed6ab485a8ce58a2d8cb6a4f55fd573f9c0" } } ], "extra": [ 1, 98, 189, 115, 120, 203, 161, 189, 43, 189, 75, 40, 64, 22, 196, 167, 133, 35, 248, 138, 68, 139, 110, 190, 194, 69, 97, 203, 56, 183, 36, 97, 182, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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