Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd79fe44ef7af3373b822b0bd4158702d8765b8c19d94072b875e0222c1c1444

Tx prefix hash: 3d95811729c2176c31ecc33118459cf9f01916c4e93ad5135a732d5aae34ea4e
Tx public key: 4eb65f14e039a35522dc5cde77c5a0f861f1c33b7527bbe64f52e927d4095fe2
Timestamp: 1638319933 Timestamp [UCT]: 2021-12-01 00:52:13 Age [y:d:h:m:s]: 03:339:00:29:13
Block: 385739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1018716 RingCT/type: yes/0
Extra: 014eb65f14e039a35522dc5cde77c5a0f861f1c33b7527bbe64f52e927d4095fe2021100000005d6e4826b000000000000000000

1 output(s) for total of 32.351682476000 dcy

stealth address amount amount idx
00: 1fb8c6a726a349f160dd2483f1161dfdd0bc54a5a4f6cb214b09eb7d8acd71bc 32.351682476000 778372 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": 385749, "vin": [ { "gen": { "height": 385739 } } ], "vout": [ { "amount": 32351682476, "target": { "key": "1fb8c6a726a349f160dd2483f1161dfdd0bc54a5a4f6cb214b09eb7d8acd71bc" } } ], "extra": [ 1, 78, 182, 95, 20, 224, 57, 163, 85, 34, 220, 92, 222, 119, 197, 160, 248, 97, 241, 195, 59, 117, 39, 187, 230, 79, 82, 233, 39, 212, 9, 95, 226, 2, 17, 0, 0, 0, 5, 214, 228, 130, 107, 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