Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7235d7c996874a11139e60382805bc63f3241d10aa5403b2b75bc25c9838f0ad

Tx prefix hash: 5b89497fb5ad55e919bde6ad3245234ea6f8e2d5137034db0d444f5df18d271c
Tx public key: bf16e44a1e3efaa9f28fe4fa1781d817f60987c8c4bd67a93b1a73c58d6eb8e6
Timestamp: 1707800990 Timestamp [UCT]: 2024-02-13 05:09:50 Age [y:d:h:m:s]: 01:122:13:41:42
Block: 956417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348601 RingCT/type: yes/0
Extra: 01bf16e44a1e3efaa9f28fe4fa1781d817f60987c8c4bd67a93b1a73c58d6eb8e602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2280fc18182048644a5ceb2a3a71bfd099d1ae39a057d95cafd67b6d042ae23 0.600000000000 1415725 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": 956427, "vin": [ { "gen": { "height": 956417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2280fc18182048644a5ceb2a3a71bfd099d1ae39a057d95cafd67b6d042ae23" } } ], "extra": [ 1, 191, 22, 228, 74, 30, 62, 250, 169, 242, 143, 228, 250, 23, 129, 216, 23, 246, 9, 135, 200, 196, 189, 103, 169, 59, 26, 115, 197, 141, 110, 184, 230, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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