Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f6c6b315387f268cf0551f311b78adc782dc7999286eea120925d088b249506

Tx prefix hash: 690a0e44578c49288dd461ca39709bd474d72b5197f30898c8555a6394962fc8
Tx public key: 403a60e4e266a5116922bd7868e244a09b679758479a4b25a9f3f93d9f31eee2
Timestamp: 1730510529 Timestamp [UCT]: 2024-11-02 01:22:09 Age [y:d:h:m:s]: 01:018:17:35:20
Block: 1144609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271820 RingCT/type: yes/0
Extra: 01403a60e4e266a5116922bd7868e244a09b679758479a4b25a9f3f93d9f31eee20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 690ec0e161f6b299fbafdc2c7c01e16d79872a7ff60379f96aef4e46da56ad7d 0.600000000000 1628872 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": 1144619, "vin": [ { "gen": { "height": 1144609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "690ec0e161f6b299fbafdc2c7c01e16d79872a7ff60379f96aef4e46da56ad7d" } } ], "extra": [ 1, 64, 58, 96, 228, 226, 102, 165, 17, 105, 34, 189, 120, 104, 226, 68, 160, 155, 103, 151, 88, 71, 154, 75, 37, 169, 243, 249, 61, 159, 49, 238, 226, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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