Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81dc8d285b858bbd6c4d9b016310940fae67f7fcddcb61191aeff0210b7ea070

Tx prefix hash: 4302f15e85dffce289e6658577f4fe3c48ffa4a6760a5070d2b0f01785fcd23d
Tx public key: 139073f023a3bdf2d98dc243cf78afadd281692cfbceb2d0ffd1f2f5354cdca9
Timestamp: 1722507985 Timestamp [UCT]: 2024-08-01 10:26:25 Age [y:d:h:m:s]: 00:247:03:35:49
Block: 1078339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176542 RingCT/type: yes/0
Extra: 01139073f023a3bdf2d98dc243cf78afadd281692cfbceb2d0ffd1f2f5354cdca9021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8e5fbeec5583b07ad5a807a5f48c90103aa757bb23585b5a269c9faebc32e2b 0.600000000000 1550916 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": 1078349, "vin": [ { "gen": { "height": 1078339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8e5fbeec5583b07ad5a807a5f48c90103aa757bb23585b5a269c9faebc32e2b" } } ], "extra": [ 1, 19, 144, 115, 240, 35, 163, 189, 242, 217, 141, 194, 67, 207, 120, 175, 173, 210, 129, 105, 44, 251, 206, 178, 208, 255, 209, 242, 245, 53, 76, 220, 169, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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