Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be999cf47276b27a13a05fd2fe8f9d9f8d5a5755ddefff794ddac67a94404b52

Tx prefix hash: 8f85eb0dce14f424aa0ac835451247df9cad0e6cd87ee203351e74c62fe499d2
Tx public key: a044676686d8148b198eb6a17e9b44c0e27bcec391460b9f0f24f16be9800a3d
Timestamp: 1724438225 Timestamp [UCT]: 2024-08-23 18:37:05 Age [y:d:h:m:s]: 00:138:10:34:26
Block: 1094364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99012 RingCT/type: yes/0
Extra: 01a044676686d8148b198eb6a17e9b44c0e27bcec391460b9f0f24f16be9800a3d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef911f6b2b1768fae50f817f841a201e366df360b7b43b258f13c3c18fba027c 0.600000000000 1569481 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": 1094374, "vin": [ { "gen": { "height": 1094364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef911f6b2b1768fae50f817f841a201e366df360b7b43b258f13c3c18fba027c" } } ], "extra": [ 1, 160, 68, 103, 102, 134, 216, 20, 139, 25, 142, 182, 161, 126, 155, 68, 192, 226, 123, 206, 195, 145, 70, 11, 159, 15, 36, 241, 107, 233, 128, 10, 61, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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