Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 352479c49af0857bdae4da2fbf6bf657511533d44ad49c707779a4315b1818c1

Tx prefix hash: 17056d15644a2d957be99e840c4c4ef3cd8da0ef571f6ecbc4bbd96a60c92028
Tx public key: a8cd34a58454ea4f994c6f38215843f547c1a4f34af6a1223b4c471fb3cfa443
Timestamp: 1718065002 Timestamp [UCT]: 2024-06-11 00:16:42 Age [y:d:h:m:s]: 01:149:02:27:37
Block: 1041520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365111 RingCT/type: yes/0
Extra: 01a8cd34a58454ea4f994c6f38215843f547c1a4f34af6a1223b4c471fb3cfa4430211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1468615b2580aeee12339389b611c49f99c65a9a8c0383b5c0a035d333b37ee 0.600000000000 1510215 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": 1041530, "vin": [ { "gen": { "height": 1041520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1468615b2580aeee12339389b611c49f99c65a9a8c0383b5c0a035d333b37ee" } } ], "extra": [ 1, 168, 205, 52, 165, 132, 84, 234, 79, 153, 76, 111, 56, 33, 88, 67, 245, 71, 193, 164, 243, 74, 246, 161, 34, 59, 76, 71, 31, 179, 207, 164, 67, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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