Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49986f6792caee4558128036c012887eaf9f069f4ae21cfdc7be264a7ff6912c

Tx prefix hash: 676a310aa9f898143dad161d908231f262718013f612c2e17364c4ba523c01b7
Tx public key: d1875a021d91e5d7ee3e1014a9a6bd29d184e8e252ec91c0f4ccc45ae56a3922
Timestamp: 1702578496 Timestamp [UCT]: 2023-12-14 18:28:16 Age [y:d:h:m:s]: 01:036:22:31:40
Block: 913121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287719 RingCT/type: yes/0
Extra: 01d1875a021d91e5d7ee3e1014a9a6bd29d184e8e252ec91c0f4ccc45ae56a392202110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08c678c2423789e0b751c6749dde9283868502bc64c87f1de0a60b3227f0eb17 0.600000000000 1370367 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": 913131, "vin": [ { "gen": { "height": 913121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08c678c2423789e0b751c6749dde9283868502bc64c87f1de0a60b3227f0eb17" } } ], "extra": [ 1, 209, 135, 90, 2, 29, 145, 229, 215, 238, 62, 16, 20, 169, 166, 189, 41, 209, 132, 232, 226, 82, 236, 145, 192, 244, 204, 196, 90, 229, 106, 57, 34, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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