Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2f56dfe4594e01e033c7c7a9c89f60a3fc416718b60a29c22f52b3c01f99b02

Tx prefix hash: e9e31741e60011af196190253a0ffc664e339f6b4ed81721f121754be0967d54
Tx public key: 5bc82c9f22fa43587528848c3b862eae66c674adf24709da6c81a760710c4921
Timestamp: 1658534791 Timestamp [UCT]: 2022-07-23 00:06:31 Age [y:d:h:m:s]: 02:333:16:47:02
Block: 549600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 759566 RingCT/type: yes/0
Extra: 015bc82c9f22fa43587528848c3b862eae66c674adf24709da6c81a760710c4921021100000002faf35c9c000000000000000000

1 output(s) for total of 9.267171133000 dcy

stealth address amount amount idx
00: 19f20cd4d3359c16fee969663e19230efc2255865d8259c26915920e98b33cb8 9.267171133000 980985 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": 549610, "vin": [ { "gen": { "height": 549600 } } ], "vout": [ { "amount": 9267171133, "target": { "key": "19f20cd4d3359c16fee969663e19230efc2255865d8259c26915920e98b33cb8" } } ], "extra": [ 1, 91, 200, 44, 159, 34, 250, 67, 88, 117, 40, 132, 140, 59, 134, 46, 174, 102, 198, 116, 173, 242, 71, 9, 218, 108, 129, 167, 96, 113, 12, 73, 33, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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