Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6343681c16a74f4ca873633ae2c5ee9111481e0f80195455e1ccbc545d5df4f

Tx prefix hash: 56f13e70c048560f18bced49d251f84e96519430a9653c87e52a18a25109a4c6
Tx public key: 32afd31df04ae822102bad70d1ed910f60d62b5faf08ffbcd12a98a9f9abc43d
Timestamp: 1706400935 Timestamp [UCT]: 2024-01-28 00:15:35 Age [y:d:h:m:s]: 01:028:11:27:13
Block: 944788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281406 RingCT/type: yes/0
Extra: 0132afd31df04ae822102bad70d1ed910f60d62b5faf08ffbcd12a98a9f9abc43d02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0182af7238b90bd1756eafe2df935f07517cd8de89f669dcb84e0355bae5362 0.600000000000 1403074 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": 944798, "vin": [ { "gen": { "height": 944788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0182af7238b90bd1756eafe2df935f07517cd8de89f669dcb84e0355bae5362" } } ], "extra": [ 1, 50, 175, 211, 29, 240, 74, 232, 34, 16, 43, 173, 112, 209, 237, 145, 15, 96, 214, 43, 95, 175, 8, 255, 188, 209, 42, 152, 169, 249, 171, 196, 61, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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