Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79a3c6c9eaa0600a9a96374e428c46d31e6774f6d44104b7ec02528d510acc9e

Tx prefix hash: 98f70d3b163c26601836bbd8bdc93280dbdf5769857f50fadc84064ed6c73211
Tx public key: 7b2ba4f1f10df5723b118825a8f3493e822d2fa663965cd4b35eca8d98e83686
Timestamp: 1711801812 Timestamp [UCT]: 2024-03-30 12:30:12 Age [y:d:h:m:s]: 00:278:09:14:46
Block: 989612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199251 RingCT/type: yes/0
Extra: 017b2ba4f1f10df5723b118825a8f3493e822d2fa663965cd4b35eca8d98e836860211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3ace8c16d5f8db3593f63c10d62d1b143a2c6c8bac0674936639a110c4dfce6 0.600000000000 1449911 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": 989622, "vin": [ { "gen": { "height": 989612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3ace8c16d5f8db3593f63c10d62d1b143a2c6c8bac0674936639a110c4dfce6" } } ], "extra": [ 1, 123, 43, 164, 241, 241, 13, 245, 114, 59, 17, 136, 37, 168, 243, 73, 62, 130, 45, 47, 166, 99, 150, 92, 212, 179, 94, 202, 141, 152, 232, 54, 134, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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