Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52e79a77ce0f2827a0b3c876c07f646006f840aa2eba1334c0264ef41f74c5f0

Tx prefix hash: 7405887a2170a7c1c05e57299952f2e9405abb0b499ec933091040a4fb65466a
Tx public key: 9fabbd61e0367c9f9a7bd09f30454e6a2a709a1705e20f21c651af11076596f5
Timestamp: 1707528212 Timestamp [UCT]: 2024-02-10 01:23:32 Age [y:d:h:m:s]: 01:017:06:24:37
Block: 954152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273356 RingCT/type: yes/0
Extra: 019fabbd61e0367c9f9a7bd09f30454e6a2a709a1705e20f21c651af11076596f50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26393a36c59671d879d05c5f6e9af1788dc1ca9aab9b65f9d02a783c03c9e020 0.600000000000 1413428 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": 954162, "vin": [ { "gen": { "height": 954152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26393a36c59671d879d05c5f6e9af1788dc1ca9aab9b65f9d02a783c03c9e020" } } ], "extra": [ 1, 159, 171, 189, 97, 224, 54, 124, 159, 154, 123, 208, 159, 48, 69, 78, 106, 42, 112, 154, 23, 5, 226, 15, 33, 198, 81, 175, 17, 7, 101, 150, 245, 2, 17, 0, 0, 0, 1, 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