Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd2dcd242a3d4bc83f2d354e825f5ea0af0e34c8857c2770967d04598fcdec42

Tx prefix hash: 83c90b4c69616aa900f81504bed5cc3922f739dec3b350e2a50c4dc02b2b3267
Tx public key: 6728e56ddb29527f2cfae6c20efe4e3453fddcedbceb257ca61f295ef03376ab
Timestamp: 1717028889 Timestamp [UCT]: 2024-05-30 00:28:09 Age [y:d:h:m:s]: 00:154:13:01:57
Block: 1032930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110625 RingCT/type: yes/0
Extra: 016728e56ddb29527f2cfae6c20efe4e3453fddcedbceb257ca61f295ef03376ab02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7341a1375fa2c56a5f6277502c7deef19a4abff99357480e3bb2b19013d3b211 0.600000000000 1501387 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": 1032940, "vin": [ { "gen": { "height": 1032930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7341a1375fa2c56a5f6277502c7deef19a4abff99357480e3bb2b19013d3b211" } } ], "extra": [ 1, 103, 40, 229, 109, 219, 41, 82, 127, 44, 250, 230, 194, 14, 254, 78, 52, 83, 253, 220, 237, 188, 235, 37, 124, 166, 31, 41, 94, 240, 51, 118, 171, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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