Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d70db5f1644c8d8fd55ac1f3d77a9545ee6ffb2b592b04d57d05758e43af4079

Tx prefix hash: 51dddb230a02b941507313f6c2d910fe39ec2c3a45521619bad9dcc593e2c3c2
Tx public key: 887ddc94a4970e542bca72a5bfdd9b8a2ea0f05ad5ccb3bf1458d708c161170b
Timestamp: 1702694347 Timestamp [UCT]: 2023-12-16 02:39:07 Age [y:d:h:m:s]: 01:328:14:27:36
Block: 914083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493698 RingCT/type: yes/0
Extra: 01887ddc94a4970e542bca72a5bfdd9b8a2ea0f05ad5ccb3bf1458d708c161170b02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ded1f14adad71b544fa525abb046642e9bfe76444a4e4eea224f335adcd6462 0.600000000000 1371365 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": 914093, "vin": [ { "gen": { "height": 914083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ded1f14adad71b544fa525abb046642e9bfe76444a4e4eea224f335adcd6462" } } ], "extra": [ 1, 136, 125, 220, 148, 164, 151, 14, 84, 43, 202, 114, 165, 191, 221, 155, 138, 46, 160, 240, 90, 213, 204, 179, 191, 20, 88, 215, 8, 193, 97, 23, 11, 2, 17, 0, 0, 0, 4, 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