Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70370372eb6f7900abf511bce18a84c3dd359fe296ee790e5a4bdbaa7815f7e1

Tx prefix hash: 4e55d4252e3b038f22672341aab451e9fc0884b29bf62dc1b8de23f1f18e62e0
Tx public key: 372b314f25f642442d9b824c226f757f4cd73fedebee76f75f0d3f317255d8ed
Timestamp: 1706035506 Timestamp [UCT]: 2024-01-23 18:45:06 Age [y:d:h:m:s]: 01:070:08:20:23
Block: 941752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311365 RingCT/type: yes/0
Extra: 01372b314f25f642442d9b824c226f757f4cd73fedebee76f75f0d3f317255d8ed0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d28a6f50005c752969ff4e73df6b6284a32fd87653e20cc03c25e088a39506f4 0.600000000000 1399908 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": 941762, "vin": [ { "gen": { "height": 941752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d28a6f50005c752969ff4e73df6b6284a32fd87653e20cc03c25e088a39506f4" } } ], "extra": [ 1, 55, 43, 49, 79, 37, 246, 66, 68, 45, 155, 130, 76, 34, 111, 117, 127, 76, 215, 63, 237, 235, 238, 118, 247, 95, 13, 63, 49, 114, 85, 216, 237, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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