Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93a04d1e4e13fec5230c39b41db32741d73a47ea943a389f49886cdab546d5cf

Tx prefix hash: a02d959744d79ab063e0148ea8014387b7ac427a96bd339b605693e173f57bc3
Tx public key: 218b756975c523141a74fdc4a8e6e6817cc0cd7759da9fe22f3cd465e60eaf29
Timestamp: 1577871622 Timestamp [UCT]: 2020-01-01 09:40:22 Age [y:d:h:m:s]: 04:330:13:54:09
Block: 36254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125477 RingCT/type: yes/0
Extra: 01218b756975c523141a74fdc4a8e6e6817cc0cd7759da9fe22f3cd465e60eaf2902110000000fc5b5978f000000000000000000

1 output(s) for total of 465.488201093000 dcy

stealth address amount amount idx
00: 072f6ac18fae7d704e3366620778edef4a6b70199da7b00c27a838a84b82e7ae 465.488201093000 61361 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": 36264, "vin": [ { "gen": { "height": 36254 } } ], "vout": [ { "amount": 465488201093, "target": { "key": "072f6ac18fae7d704e3366620778edef4a6b70199da7b00c27a838a84b82e7ae" } } ], "extra": [ 1, 33, 139, 117, 105, 117, 197, 35, 20, 26, 116, 253, 196, 168, 230, 230, 129, 124, 192, 205, 119, 89, 218, 159, 226, 47, 60, 212, 101, 230, 14, 175, 41, 2, 17, 0, 0, 0, 15, 197, 181, 151, 143, 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