Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc5359ca88c1a6cf29cea10c3c6ae48ee51514dedd49f996749c204f69ab1a71

Tx prefix hash: feab2cae6a1507801e2bdf3d8aaf72d5c918703cda942e9ecc3d52d1405eff71
Tx public key: 80680f816ecfd48a0cd2bede8adb941259695321e8e37658c550f41320d00ca5
Timestamp: 1698678089 Timestamp [UCT]: 2023-10-30 15:01:29 Age [y:d:h:m:s]: 02:036:02:39:07
Block: 881006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545424 RingCT/type: yes/0
Extra: 0180680f816ecfd48a0cd2bede8adb941259695321e8e37658c550f41320d00ca5021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.739369294000 dcy

stealth address amount amount idx
00: 00236ee572ce71ecb19c55d7945c3efc1f4431e9b5aa45c2d1e3e1b46246e950 0.739369294000 1336576 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": 881016, "vin": [ { "gen": { "height": 881006 } } ], "vout": [ { "amount": 739369294, "target": { "key": "00236ee572ce71ecb19c55d7945c3efc1f4431e9b5aa45c2d1e3e1b46246e950" } } ], "extra": [ 1, 128, 104, 15, 129, 110, 207, 212, 138, 12, 210, 190, 222, 138, 219, 148, 18, 89, 105, 83, 33, 232, 227, 118, 88, 197, 80, 244, 19, 32, 208, 12, 165, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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