Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 612cdf6aa71912cd99404f8c01c1a2b661e82241c6a4e15a76f39f3bf954368f

Tx prefix hash: 742ec633aa75bf2727c17109fcd511f51244f1a46c10e812e212c957dadd463f
Tx public key: 8a1cc600bccadd542d35153bfd99291e581e9707d87d8d51fa2f026835c12b21
Timestamp: 1699836694 Timestamp [UCT]: 2023-11-13 00:51:34 Age [y:d:h:m:s]: 01:079:21:53:32
Block: 890408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318245 RingCT/type: yes/0
Extra: 018a1cc600bccadd542d35153bfd99291e581e9707d87d8d51fa2f026835c12b21021100000006faf35c9c000000000000000000

1 output(s) for total of 0.688190491000 dcy

stealth address amount amount idx
00: 1dfdfab3ddd840226ce75db7f29b62ccef208720dd47881e83ad6bed55416f35 0.688190491000 1346431 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": 890418, "vin": [ { "gen": { "height": 890408 } } ], "vout": [ { "amount": 688190491, "target": { "key": "1dfdfab3ddd840226ce75db7f29b62ccef208720dd47881e83ad6bed55416f35" } } ], "extra": [ 1, 138, 28, 198, 0, 188, 202, 221, 84, 45, 53, 21, 59, 253, 153, 41, 30, 88, 30, 151, 7, 216, 125, 141, 81, 250, 47, 2, 104, 53, 193, 43, 33, 2, 17, 0, 0, 0, 6, 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