Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6ac403c8511fec0ef0e4d582f7abb1bd591eb307c1aafde1d3e68c52b2a9ba1

Tx prefix hash: cf22e2421e409b56dfdce629e50313574df347309bb111f26c560901eb750b24
Tx public key: 36b5ebd41fac3be8fe515b610dccc6f570ad880364ca991bc0dc53ffcd01750a
Timestamp: 1673080459 Timestamp [UCT]: 2023-01-07 08:34:19 Age [y:d:h:m:s]: 02:142:12:24:19
Block: 669421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 623594 RingCT/type: yes/0
Extra: 0136b5ebd41fac3be8fe515b610dccc6f570ad880364ca991bc0dc53ffcd01750a02110000000152542ceb000000000000000000

1 output(s) for total of 3.714756020000 dcy

stealth address amount amount idx
00: 501431eb8462fea3d0e66d7f67e9b930a444ba38790dd2cc6050da4e68546170 3.714756020000 1110738 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": 669431, "vin": [ { "gen": { "height": 669421 } } ], "vout": [ { "amount": 3714756020, "target": { "key": "501431eb8462fea3d0e66d7f67e9b930a444ba38790dd2cc6050da4e68546170" } } ], "extra": [ 1, 54, 181, 235, 212, 31, 172, 59, 232, 254, 81, 91, 97, 13, 204, 198, 245, 112, 173, 136, 3, 100, 202, 153, 27, 192, 220, 83, 255, 205, 1, 117, 10, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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