Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbc3eff4e500b0891fc392a713218aeb5c4d73cbad4dd09475e0a4fec92909e5

Tx prefix hash: 82642ad3c366ca3a6c0b24aafb45e9bfb7ef08e5c5a251c35adf6b854b0ef339
Tx public key: 477f70642850f5db6557c95a9c00c025b85e2ab6b0711f1cc552e779ff8fb516
Timestamp: 1745045352 Timestamp [UCT]: 2025-04-19 06:49:12 Age [y:d:h:m:s]: 00:249:01:44:10
Block: 1264679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175779 RingCT/type: yes/0
Extra: 01477f70642850f5db6557c95a9c00c025b85e2ab6b0711f1cc552e779ff8fb5160211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1774d0964b5a99e507b352d92efe6465223c7fb67be6f1fcfa337b26782efe6 0.600000000000 1751878 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": 1264689, "vin": [ { "gen": { "height": 1264679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1774d0964b5a99e507b352d92efe6465223c7fb67be6f1fcfa337b26782efe6" } } ], "extra": [ 1, 71, 127, 112, 100, 40, 80, 245, 219, 101, 87, 201, 90, 156, 0, 192, 37, 184, 94, 42, 182, 176, 113, 31, 28, 197, 82, 231, 121, 255, 143, 181, 22, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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