Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcaf0c02de26748abb1c6573e9c54e8397e965054db4825a32d419608d313816

Tx prefix hash: 1a71a1c1268de69562de1870a5e496524ccb26ddd2e38e896a23e57c927f3e93
Tx public key: dce84936cc8867810623b2ca4ac5302bf9d4831f3e1b7b9445d3d4d0a7b57759
Timestamp: 1736995436 Timestamp [UCT]: 2025-01-16 02:43:56 Age [y:d:h:m:s]: 00:302:04:21:23
Block: 1198306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213484 RingCT/type: yes/0
Extra: 01dce84936cc8867810623b2ca4ac5302bf9d4831f3e1b7b9445d3d4d0a7b57759021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7025ae5ac7bd0b4356a3f908b76f924c4cd08bf60a321c44f6ae74546858ec4c 0.600000000000 1684929 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": 1198316, "vin": [ { "gen": { "height": 1198306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7025ae5ac7bd0b4356a3f908b76f924c4cd08bf60a321c44f6ae74546858ec4c" } } ], "extra": [ 1, 220, 232, 73, 54, 204, 136, 103, 129, 6, 35, 178, 202, 74, 197, 48, 43, 249, 212, 131, 31, 62, 27, 123, 148, 69, 211, 212, 208, 167, 181, 119, 89, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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