Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44e5202622a41a5165f8fb737e1089672e3c4cd7745447679dd4d5c920a6db4d

Tx prefix hash: cba79b5d798d993c349e8f37cbf5322abe0ceb9cadc64126eb5eb929113cfa4a
Tx public key: 10320804e88f4d355e016b023ddadc13b8c7e872845c64a1880cca1aa3191f38
Timestamp: 1672557662 Timestamp [UCT]: 2023-01-01 07:21:02 Age [y:d:h:m:s]: 02:134:20:59:39
Block: 665095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 618114 RingCT/type: yes/0
Extra: 0110320804e88f4d355e016b023ddadc13b8c7e872845c64a1880cca1aa3191f38021100000002e6d27f9c000000000000000000

1 output(s) for total of 3.839406850000 dcy

stealth address amount amount idx
00: d7f9921324cedb1beebed1cf11fed20653a773a5098d9a5a960c3be96bc063e6 3.839406850000 1106110 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": 665105, "vin": [ { "gen": { "height": 665095 } } ], "vout": [ { "amount": 3839406850, "target": { "key": "d7f9921324cedb1beebed1cf11fed20653a773a5098d9a5a960c3be96bc063e6" } } ], "extra": [ 1, 16, 50, 8, 4, 232, 143, 77, 53, 94, 1, 107, 2, 61, 218, 220, 19, 184, 199, 232, 114, 132, 92, 100, 161, 136, 12, 202, 26, 163, 25, 31, 56, 2, 17, 0, 0, 0, 2, 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