Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 831bc567a174f986e290263ffa490bc6c151bfcf528e330dc6d5b8dce5f80392

Tx prefix hash: 8cf5269561ecc63d14b56dd826e50956e988b517933de2e77a4c0337130af1a3
Tx public key: 60083249ecf4e5a17cb1ff0cfd4f3ebe7d7d761c863f8e478bc70b585d475c00
Timestamp: 1735212101 Timestamp [UCT]: 2024-12-26 11:21:41 Age [y:d:h:m:s]: 00:089:05:09:00
Block: 1183556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63530 RingCT/type: yes/0
Extra: 0160083249ecf4e5a17cb1ff0cfd4f3ebe7d7d761c863f8e478bc70b585d475c00021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1b34653ce9926c45d51256071a7d1f13664240cd886fff5eaa166e2abd23375 0.600000000000 1670001 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": 1183566, "vin": [ { "gen": { "height": 1183556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1b34653ce9926c45d51256071a7d1f13664240cd886fff5eaa166e2abd23375" } } ], "extra": [ 1, 96, 8, 50, 73, 236, 244, 229, 161, 124, 177, 255, 12, 253, 79, 62, 190, 125, 125, 118, 28, 134, 63, 142, 71, 139, 199, 11, 88, 93, 71, 92, 0, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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