Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7615aecc0973e9bbbf44bc709051552d5bdfbfa4ab6b225c1c71e7215cbe602b

Tx prefix hash: b9aab85c7d92bba23d427730825ac455b7f8ab7c8b136ea73ecbeb849d119d45
Tx public key: 2b3f938c9b651635d91a2c17708edcaa9a52e7475c6547ba9c0c2a6bcaf17575
Timestamp: 1728983802 Timestamp [UCT]: 2024-10-15 09:16:42 Age [y:d:h:m:s]: 00:228:08:20:56
Block: 1132045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163015 RingCT/type: yes/0
Extra: 012b3f938c9b651635d91a2c17708edcaa9a52e7475c6547ba9c0c2a6bcaf17575021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d18c446b4c2333e5bd940ff0038f94d732805cf447a60561dd42806d1053a2e4 0.600000000000 1614954 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": 1132055, "vin": [ { "gen": { "height": 1132045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d18c446b4c2333e5bd940ff0038f94d732805cf447a60561dd42806d1053a2e4" } } ], "extra": [ 1, 43, 63, 147, 140, 155, 101, 22, 53, 217, 26, 44, 23, 112, 142, 220, 170, 154, 82, 231, 71, 92, 101, 71, 186, 156, 12, 42, 107, 202, 241, 117, 117, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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