Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07ce759456329c05abe7d9911be9653b5367212efd68f16da5b0db31abec242d

Tx prefix hash: 169675c1fbd55ff9439891935c7f0fc9a8f5dec67df0ea4a9a4268d215441f80
Tx public key: c0867a0ab15ab1bb06b477ea3e56cfc33a0b287d84b38b9b22b435acd9061d13
Timestamp: 1581986458 Timestamp [UCT]: 2020-02-18 00:40:58 Age [y:d:h:m:s]: 04:262:18:53:41
Block: 67085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080207 RingCT/type: yes/0
Extra: 01c0867a0ab15ab1bb06b477ea3e56cfc33a0b287d84b38b9b22b435acd9061d130211000000224ac5aa02000000000000000000

1 output(s) for total of 367.892009034000 dcy

stealth address amount amount idx
00: 61b52f0e5131e47bd5557c4166726496a0ba72562bb23feccad3600f6ff3611f 367.892009034000 123602 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": 67095, "vin": [ { "gen": { "height": 67085 } } ], "vout": [ { "amount": 367892009034, "target": { "key": "61b52f0e5131e47bd5557c4166726496a0ba72562bb23feccad3600f6ff3611f" } } ], "extra": [ 1, 192, 134, 122, 10, 177, 90, 177, 187, 6, 180, 119, 234, 62, 86, 207, 195, 58, 11, 40, 125, 132, 179, 139, 155, 34, 180, 53, 172, 217, 6, 29, 19, 2, 17, 0, 0, 0, 34, 74, 197, 170, 2, 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