Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8267228d307320704e6efb1ec357e1460572631e3013d9225eb4a060f34c1753

Tx prefix hash: 6ab7b59c7d2a93491b45d6adc4c2d6d1f3dd0f835d9c1d6d8ec36d0b2c07863e
Tx public key: 44b35c9f5c0e52e9850ea16372df6728f64dbe4ebaa8c5d9c788daeb0d42b938
Timestamp: 1708978263 Timestamp [UCT]: 2024-02-26 20:11:03 Age [y:d:h:m:s]: 01:251:13:18:57
Block: 966191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438510 RingCT/type: yes/0
Extra: 0144b35c9f5c0e52e9850ea16372df6728f64dbe4ebaa8c5d9c788daeb0d42b93802110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44f88b719d06121ec9bbddad98fa6ad69e12fa75b8750af4eaf5663e1a93638d 0.600000000000 1425948 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": 966201, "vin": [ { "gen": { "height": 966191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44f88b719d06121ec9bbddad98fa6ad69e12fa75b8750af4eaf5663e1a93638d" } } ], "extra": [ 1, 68, 179, 92, 159, 92, 14, 82, 233, 133, 14, 161, 99, 114, 223, 103, 40, 246, 77, 190, 78, 186, 168, 197, 217, 199, 136, 218, 235, 13, 66, 185, 56, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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