Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8731bf1429e2a4ff55f6e9a815caffa7c3218399cbea868c0ae619de3875e94d

Tx prefix hash: 83f7fa089a96242512fd929d2fa85346fb27dadbe929666513d07d95a0250826
Tx public key: 7d39ecc9dd9ed6fa80d97f5513d4b096810566abe048ee7938a7b791a3a6299a
Timestamp: 1702750496 Timestamp [UCT]: 2023-12-16 18:14:56 Age [y:d:h:m:s]: 01:329:19:06:55
Block: 914551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494551 RingCT/type: yes/0
Extra: 017d39ecc9dd9ed6fa80d97f5513d4b096810566abe048ee7938a7b791a3a6299a021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e7355c32836025a534f1729be66991e28ae6dc9dc1f64970488cb6739bdcb02 0.600000000000 1371877 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": 914561, "vin": [ { "gen": { "height": 914551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e7355c32836025a534f1729be66991e28ae6dc9dc1f64970488cb6739bdcb02" } } ], "extra": [ 1, 125, 57, 236, 201, 221, 158, 214, 250, 128, 217, 127, 85, 19, 212, 176, 150, 129, 5, 102, 171, 224, 72, 238, 121, 56, 167, 183, 145, 163, 166, 41, 154, 2, 17, 0, 0, 0, 5, 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