Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec130c4d65d8d227a7367c0ac6cdcf0fe76af299ccb3cb07d584d520af737cc

Tx prefix hash: b83e649bac4d077e81f6e213e04e670ca3de046720619c3e6d9730a7ead5605e
Tx public key: 6f9844f3b1bbd1a9fa91dd549c91162bc9c36b70a1301737f6be2b56338ce997
Timestamp: 1702694369 Timestamp [UCT]: 2023-12-16 02:39:29 Age [y:d:h:m:s]: 01:152:05:28:45
Block: 914084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369950 RingCT/type: yes/0
Extra: 016f9844f3b1bbd1a9fa91dd549c91162bc9c36b70a1301737f6be2b56338ce99702110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b355963f938c62d1d683d3140e59e6e1ad1f09368158b936453eabc855ada99 0.600000000000 1371366 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": 914094, "vin": [ { "gen": { "height": 914084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b355963f938c62d1d683d3140e59e6e1ad1f09368158b936453eabc855ada99" } } ], "extra": [ 1, 111, 152, 68, 243, 177, 187, 209, 169, 250, 145, 221, 84, 156, 145, 22, 43, 201, 195, 107, 112, 161, 48, 23, 55, 246, 190, 43, 86, 51, 140, 233, 151, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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