Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58cde03fb72fd86ec2744f1140f8fdf0f533d711d9335dfa6447c16796ab27f6

Tx prefix hash: e73b6ca10727d4f76aafcd7f6a5557de61b906acd0117ba869306aaabd858e2a
Tx public key: d3ba3024f2af4fcf7a4c4934b6f5fbf5f2e9be6300a0225630d4c5ba7790341e
Timestamp: 1695329768 Timestamp [UCT]: 2023-09-21 20:56:08 Age [y:d:h:m:s]: 01:274:22:59:07
Block: 853214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457430 RingCT/type: yes/0
Extra: 01d3ba3024f2af4fcf7a4c4934b6f5fbf5f2e9be6300a0225630d4c5ba7790341e0211000000084b8f5122000000000000000000

1 output(s) for total of 0.914033553000 dcy

stealth address amount amount idx
00: fbc195f532f099c579bbc35f6464ae3c8e464b47d93524f2d8f5cf405e722d9c 0.914033553000 1307100 of 0

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": 853224, "vin": [ { "gen": { "height": 853214 } } ], "vout": [ { "amount": 914033553, "target": { "key": "fbc195f532f099c579bbc35f6464ae3c8e464b47d93524f2d8f5cf405e722d9c" } } ], "extra": [ 1, 211, 186, 48, 36, 242, 175, 79, 207, 122, 76, 73, 52, 182, 245, 251, 245, 242, 233, 190, 99, 0, 160, 34, 86, 48, 212, 197, 186, 119, 144, 52, 30, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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