Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d301170ee7383e30cf8aa01a2e9e39933da8f0f838091dba132fff0fca5010c3

Tx prefix hash: 278a3b6909031ae21bd752dabdd27d84e67ef73d01e7c61f8426e4ba95fac780
Tx public key: 37a48fa2d2b87d9fb466cd278b4c9191166179e6691fb8999a51efc0b2e0ae15
Timestamp: 1717132639 Timestamp [UCT]: 2024-05-31 05:17:19 Age [y:d:h:m:s]: 01:017:16:00:37
Block: 1033782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273416 RingCT/type: yes/0
Extra: 0137a48fa2d2b87d9fb466cd278b4c9191166179e6691fb8999a51efc0b2e0ae1502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64c379fcd7bc6162bf4d61c77126400ae0e2d8279509a7a2aac9c07a0a163b30 0.600000000000 1502255 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": 1033792, "vin": [ { "gen": { "height": 1033782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64c379fcd7bc6162bf4d61c77126400ae0e2d8279509a7a2aac9c07a0a163b30" } } ], "extra": [ 1, 55, 164, 143, 162, 210, 184, 125, 159, 180, 102, 205, 39, 139, 76, 145, 145, 22, 97, 121, 230, 105, 31, 184, 153, 154, 81, 239, 192, 178, 224, 174, 21, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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