Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a67ec2ddf2f0fc603138fa17eb0e8b5192cc022830253fbf0e15102a7bff658

Tx prefix hash: aaa45e1db9c88d1bcd544a93b5fa6db7cc79ea84511c11f96b505683dad11b23
Tx public key: 8bfaf18f2c385a5f182683c9e1ff140e1a1c0c150a953ce7b7d0d51e6ce865f2
Timestamp: 1717628260 Timestamp [UCT]: 2024-06-05 22:57:40 Age [y:d:h:m:s]: 01:009:13:53:48
Block: 1037894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267647 RingCT/type: yes/0
Extra: 018bfaf18f2c385a5f182683c9e1ff140e1a1c0c150a953ce7b7d0d51e6ce865f202110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52565362ffb8cbe8438ac0f773f5c68188719572a75e2034c9a8d5bc9b041e0b 0.600000000000 1506451 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": 1037904, "vin": [ { "gen": { "height": 1037894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52565362ffb8cbe8438ac0f773f5c68188719572a75e2034c9a8d5bc9b041e0b" } } ], "extra": [ 1, 139, 250, 241, 143, 44, 56, 90, 95, 24, 38, 131, 201, 225, 255, 20, 14, 26, 28, 12, 21, 10, 149, 60, 231, 183, 208, 213, 30, 108, 232, 101, 242, 2, 17, 0, 0, 0, 12, 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