Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a68b13d85b86841a0aee9ec235dfb5df88aba761f0b13a20911c045a920515c

Tx prefix hash: ec9af9af1b5f637c8e8de6ffaee8733aada187139779d46b3aa21181f6f5c03e
Tx public key: d9c3babc8c047696fde41d4b99a3905cc8d93212240881671753a225c2a7dbfa
Timestamp: 1720290210 Timestamp [UCT]: 2024-07-06 18:23:30 Age [y:d:h:m:s]: 01:130:21:54:46
Block: 1059957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352094 RingCT/type: yes/0
Extra: 01d9c3babc8c047696fde41d4b99a3905cc8d93212240881671753a225c2a7dbfa02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 655a794b3ae1a62983240ff949e175bf14bc5f1f3cfbfbb7062c95f06f549d3f 0.600000000000 1530428 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": 1059967, "vin": [ { "gen": { "height": 1059957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "655a794b3ae1a62983240ff949e175bf14bc5f1f3cfbfbb7062c95f06f549d3f" } } ], "extra": [ 1, 217, 195, 186, 188, 140, 4, 118, 150, 253, 228, 29, 75, 153, 163, 144, 92, 200, 217, 50, 18, 36, 8, 129, 103, 23, 83, 162, 37, 194, 167, 219, 250, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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