Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cbc1d5cc6086e17caa10ee9d0b0a972876ea8bbb943bc09c08edc931fd0e7fe

Tx prefix hash: b30d52d40773ace3c8c3b8c58917c3e12f56c8f37b4bcdb470f39606bac9c76a
Tx public key: db19d63d78dce4ade276bf247a7134a07835a7d1bab1e5fb012c6577c8246247
Timestamp: 1728169657 Timestamp [UCT]: 2024-10-05 23:07:37 Age [y:d:h:m:s]: 00:012:16:20:47
Block: 1125291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9079 RingCT/type: yes/0
Extra: 01db19d63d78dce4ade276bf247a7134a07835a7d1bab1e5fb012c6577c824624702110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3c977234f71ed652190ef4184f17f4882982a749c1d35ef291d02d41f74d6e5 0.600000000000 1607968 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": 1125301, "vin": [ { "gen": { "height": 1125291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3c977234f71ed652190ef4184f17f4882982a749c1d35ef291d02d41f74d6e5" } } ], "extra": [ 1, 219, 25, 214, 61, 120, 220, 228, 173, 226, 118, 191, 36, 122, 113, 52, 160, 120, 53, 167, 209, 186, 177, 229, 251, 1, 44, 101, 119, 200, 36, 98, 71, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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