Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e730daafb5dac046e73b4bf6b51f4c6e5a740e36b2488fe29446fd17d0054ff

Tx prefix hash: 4f93d02b57a4929a353ce3060ac5e3733f10d390f9e1308af5071832d6f60bfe
Tx public key: 0320b2d9971584142a4ce842ae414869d957b5efa7f4e66017738cdc5fb97482
Timestamp: 1730148107 Timestamp [UCT]: 2024-10-28 20:41:47 Age [y:d:h:m:s]: 00:150:05:34:20
Block: 1141613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107200 RingCT/type: yes/0
Extra: 010320b2d9971584142a4ce842ae414869d957b5efa7f4e66017738cdc5fb97482021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f328f02ade4a938fd707fe1dc2b56cef5e5d4c91988de559e06ba27489577713 0.600000000000 1625422 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": 1141623, "vin": [ { "gen": { "height": 1141613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f328f02ade4a938fd707fe1dc2b56cef5e5d4c91988de559e06ba27489577713" } } ], "extra": [ 1, 3, 32, 178, 217, 151, 21, 132, 20, 42, 76, 232, 66, 174, 65, 72, 105, 217, 87, 181, 239, 167, 244, 230, 96, 23, 115, 140, 220, 95, 185, 116, 130, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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