Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30d43d70915a954e1005eed8ce371f3e0087d5052e42e910a0e3e159b7339f51

Tx prefix hash: e0781c1cb16afa2cc8612e23a4f6ae921016b6ace07c601d1eafa7d8a8e50672
Tx public key: 07402d77eac56b1c43ef49db0a9617cb4ccb1419378168cb1003a81bd5b157b0
Timestamp: 1734732906 Timestamp [UCT]: 2024-12-20 22:15:06 Age [y:d:h:m:s]: 00:092:08:55:48
Block: 1179611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65769 RingCT/type: yes/0
Extra: 0107402d77eac56b1c43ef49db0a9617cb4ccb1419378168cb1003a81bd5b157b00211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f13e44258338b34f63c2cacf08442d5749ae68e3502e0c6a33e15f77aa9769a 0.600000000000 1666010 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": 1179621, "vin": [ { "gen": { "height": 1179611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f13e44258338b34f63c2cacf08442d5749ae68e3502e0c6a33e15f77aa9769a" } } ], "extra": [ 1, 7, 64, 45, 119, 234, 197, 107, 28, 67, 239, 73, 219, 10, 150, 23, 203, 76, 203, 20, 25, 55, 129, 104, 203, 16, 3, 168, 27, 213, 177, 87, 176, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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