Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21fee4c29d55f01e35086754eb799d7d124dcf4ac718af8f9e4fd0f887dea9cc

Tx prefix hash: 07c85059826da3c28c350d0eae987120fe649ea09fd4cd0fdd13f139b9179c56
Tx public key: 2f76b04ba26f97de4f3b206c233d07e8920ab64a50053ee4bc070a93460abcf8
Timestamp: 1700806602 Timestamp [UCT]: 2023-11-24 06:16:42 Age [y:d:h:m:s]: 01:172:13:49:19
Block: 898431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384540 RingCT/type: yes/0
Extra: 012f76b04ba26f97de4f3b206c233d07e8920ab64a50053ee4bc070a93460abcf802110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.647329093000 dcy

stealth address amount amount idx
00: 5f8379256355f41d87ae014dc7c4b3bddf8c4932d266e81900bac3cffc6e33d5 0.647329093000 1354844 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": 898441, "vin": [ { "gen": { "height": 898431 } } ], "vout": [ { "amount": 647329093, "target": { "key": "5f8379256355f41d87ae014dc7c4b3bddf8c4932d266e81900bac3cffc6e33d5" } } ], "extra": [ 1, 47, 118, 176, 75, 162, 111, 151, 222, 79, 59, 32, 108, 35, 61, 7, 232, 146, 10, 182, 74, 80, 5, 62, 228, 188, 7, 10, 147, 70, 10, 188, 248, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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