Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1083382cd1e985c2ba4dbe5f3ca7c7ba8ef07ae9a49138245d086a5f2378e96

Tx prefix hash: e813e228acd3245bdf449a958544317969dbf07e959a05ee2deb5a5296225f5e
Tx public key: d5e8d96911391f9be094f361a1db9a1464216b0f6bbaa70bdefc7278e44c75ed
Timestamp: 1696107917 Timestamp [UCT]: 2023-09-30 21:05:17 Age [y:d:h:m:s]: 01:234:17:27:21
Block: 859686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428844 RingCT/type: yes/0
Extra: 01d5e8d96911391f9be094f361a1db9a1464216b0f6bbaa70bdefc7278e44c75ed02110000000933af99f4000000000000000000

1 output(s) for total of 0.869968348000 dcy

stealth address amount amount idx
00: a451b2334fa300be1fe892516a07c04536f95985f47a04f6bea19f6bfbb4e771 0.869968348000 1313926 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": 859696, "vin": [ { "gen": { "height": 859686 } } ], "vout": [ { "amount": 869968348, "target": { "key": "a451b2334fa300be1fe892516a07c04536f95985f47a04f6bea19f6bfbb4e771" } } ], "extra": [ 1, 213, 232, 217, 105, 17, 57, 31, 155, 224, 148, 243, 97, 161, 219, 154, 20, 100, 33, 107, 15, 107, 186, 167, 11, 222, 252, 114, 120, 228, 76, 117, 237, 2, 17, 0, 0, 0, 9, 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