Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7935cd903656600cd1589448ae1abc71678dd6ec95d755dc37affcc61eff169

Tx prefix hash: 2650a219a955e18eb514a928f400fee3b25aead3da95d67825de446633b91b1d
Tx public key: 7e402d603a6726f1a7df5f3445477f927e524f3f8e02c95b2ae91d22cc9235d9
Timestamp: 1728444671 Timestamp [UCT]: 2024-10-09 03:31:11 Age [y:d:h:m:s]: 01:031:18:10:10
Block: 1127565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281072 RingCT/type: yes/0
Extra: 017e402d603a6726f1a7df5f3445477f927e524f3f8e02c95b2ae91d22cc9235d902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b3607c3a41741045baa753a57765ef54389335f6c7b66c3091fc0065fa86730 0.600000000000 1610372 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": 1127575, "vin": [ { "gen": { "height": 1127565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b3607c3a41741045baa753a57765ef54389335f6c7b66c3091fc0065fa86730" } } ], "extra": [ 1, 126, 64, 45, 96, 58, 103, 38, 241, 167, 223, 95, 52, 69, 71, 127, 146, 126, 82, 79, 63, 142, 2, 201, 91, 42, 233, 29, 34, 204, 146, 53, 217, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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