Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f61975290a843dedf620b865c80da7b266952b1cb04948edba715967089b7b81

Tx prefix hash: 6f6de0e7281c2786225c05087d198873d6c57d3797272c3747e2ba6cd7c0138d
Tx public key: 446626f6c2025916a691a0bb017acccd0d9a3119dd9ee1e511a640f366db0fb3
Timestamp: 1705503181 Timestamp [UCT]: 2024-01-17 14:53:01 Age [y:d:h:m:s]: 01:305:06:35:08
Block: 937351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477008 RingCT/type: yes/0
Extra: 01446626f6c2025916a691a0bb017acccd0d9a3119dd9ee1e511a640f366db0fb30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99659041f5c2d11b55b2c3ff8bb32fd8502e2e3e68e8c57386f198247f97c25c 0.600000000000 1395401 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": 937361, "vin": [ { "gen": { "height": 937351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99659041f5c2d11b55b2c3ff8bb32fd8502e2e3e68e8c57386f198247f97c25c" } } ], "extra": [ 1, 68, 102, 38, 246, 194, 2, 89, 22, 166, 145, 160, 187, 1, 122, 204, 205, 13, 154, 49, 25, 221, 158, 225, 229, 17, 166, 64, 243, 102, 219, 15, 179, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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