Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 868a28896bf0e42fd72597e22ba468b715cef89cb6e3af04ee0f7142b01b44b6

Tx prefix hash: 4070bbfca8b4932e547f3deccc6d88dc919d0e506ab29ab050ceda86e774afad
Tx public key: d653f711527e9ff97f37aded9957e7fb8af374ed6f6698a3b3b31e7bf4a320fa
Timestamp: 1659525533 Timestamp [UCT]: 2022-08-03 11:18:53 Age [y:d:h:m:s]: 02:158:04:41:33
Block: 557778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 634490 RingCT/type: yes/0
Extra: 01d653f711527e9ff97f37aded9957e7fb8af374ed6f6698a3b3b31e7bf4a320fa02110000000765468698000000000000000000

1 output(s) for total of 8.706629465000 dcy

stealth address amount amount idx
00: 225c615878eaf6b367441a40c66a7e7b7d4379fddea7a6f0aa830a0ff78bc1ef 8.706629465000 989822 of 0

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": 557788, "vin": [ { "gen": { "height": 557778 } } ], "vout": [ { "amount": 8706629465, "target": { "key": "225c615878eaf6b367441a40c66a7e7b7d4379fddea7a6f0aa830a0ff78bc1ef" } } ], "extra": [ 1, 214, 83, 247, 17, 82, 126, 159, 249, 127, 55, 173, 237, 153, 87, 231, 251, 138, 243, 116, 237, 111, 102, 152, 163, 179, 179, 30, 123, 244, 163, 32, 250, 2, 17, 0, 0, 0, 7, 101, 70, 134, 152, 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