Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25d0caf50d1c44e170bcd91b1aaeff569186956b949a59a523afb80a4069c8b4

Tx prefix hash: 446b8ce36a7c100fe092f8e4f8b8bbca40a8ca1a3f0a24416c081677c30bf302
Tx public key: b4aff6c166de0aa795b02fbc378c9ee60e052c48039874bd047192ce3fb3af9b
Timestamp: 1736433769 Timestamp [UCT]: 2025-01-09 14:42:49 Age [y:d:h:m:s]: 00:085:19:20:07
Block: 1193659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61107 RingCT/type: yes/0
Extra: 01b4aff6c166de0aa795b02fbc378c9ee60e052c48039874bd047192ce3fb3af9b0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b1e36bfd12e8635a729b49a510a7b44cfc323cca94d155bcce6dc552b466820 0.600000000000 1680222 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": 1193669, "vin": [ { "gen": { "height": 1193659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b1e36bfd12e8635a729b49a510a7b44cfc323cca94d155bcce6dc552b466820" } } ], "extra": [ 1, 180, 175, 246, 193, 102, 222, 10, 167, 149, 176, 47, 188, 55, 140, 158, 230, 14, 5, 44, 72, 3, 152, 116, 189, 4, 113, 146, 206, 63, 179, 175, 155, 2, 17, 0, 0, 0, 7, 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