Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 012af0f0844c36e8ac7eb16b7cf5dec3085838513a68a0903d2c975cc404a1dc

Tx prefix hash: 175eacb5e90452ab490972b298a5634dc7b7997f0b9ec68ff1c56c056b222dac
Tx public key: ef2b6326a782cda6de86dc4ae5166b19a0ca8534d888d4149e38867bbd18e8eb
Timestamp: 1704535852 Timestamp [UCT]: 2024-01-06 10:10:52 Age [y:d:h:m:s]: 01:304:12:15:38
Block: 929329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476451 RingCT/type: yes/0
Extra: 01ef2b6326a782cda6de86dc4ae5166b19a0ca8534d888d4149e38867bbd18e8eb02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9bccda73c02754b77e7008a7007aa76b7013b27fd940a3bd119fe844a9f55f8 0.600000000000 1387201 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": 929339, "vin": [ { "gen": { "height": 929329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9bccda73c02754b77e7008a7007aa76b7013b27fd940a3bd119fe844a9f55f8" } } ], "extra": [ 1, 239, 43, 99, 38, 167, 130, 205, 166, 222, 134, 220, 74, 229, 22, 107, 25, 160, 202, 133, 52, 216, 136, 212, 20, 158, 56, 134, 123, 189, 24, 232, 235, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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