Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46fc10a3069e6ed70a8b4f7050c3b0fb57f6c294c8ad2213e4f760ae058b8670

Tx prefix hash: ded03cac331c6808dd51218e749c8edae547762e0980c1f0f3de876a300cd314
Tx public key: 54fe4f4650278ccb88d5707c570673e64e3475e526493ca8dcd47b570caff68c
Timestamp: 1714166061 Timestamp [UCT]: 2024-04-26 21:14:21 Age [y:d:h:m:s]: 01:035:23:42:33
Block: 1009181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286687 RingCT/type: yes/0
Extra: 0154fe4f4650278ccb88d5707c570673e64e3475e526493ca8dcd47b570caff68c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 823b4b686d662af3c5838826796345c6ca6a40ea61e7057c15480842c90aa0f2 0.600000000000 1470781 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": 1009191, "vin": [ { "gen": { "height": 1009181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "823b4b686d662af3c5838826796345c6ca6a40ea61e7057c15480842c90aa0f2" } } ], "extra": [ 1, 84, 254, 79, 70, 80, 39, 140, 203, 136, 213, 112, 124, 87, 6, 115, 230, 78, 52, 117, 229, 38, 73, 60, 168, 220, 212, 123, 87, 12, 175, 246, 140, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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