Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa934d51c569aecc26d86443bc7660c173a9a2dc2452461bfde6255cb75c008

Tx prefix hash: a62f0fa1cf6d64c4e167a7c2779327e8f6cc5f80688d68275d8b0d3784ef1c78
Tx public key: fd849972f083d05a2696f81041f211fcb24c08ad3ea831d8404174bc6a78c7d0
Timestamp: 1706247431 Timestamp [UCT]: 2024-01-26 05:37:11 Age [y:d:h:m:s]: 01:031:06:47:06
Block: 943511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283417 RingCT/type: yes/0
Extra: 01fd849972f083d05a2696f81041f211fcb24c08ad3ea831d8404174bc6a78c7d002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 754063971093d8562bd57eb648845ecd2a51a7f91c90e7cb56c732bac5175813 0.600000000000 1401719 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": 943521, "vin": [ { "gen": { "height": 943511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "754063971093d8562bd57eb648845ecd2a51a7f91c90e7cb56c732bac5175813" } } ], "extra": [ 1, 253, 132, 153, 114, 240, 131, 208, 90, 38, 150, 248, 16, 65, 242, 17, 252, 178, 76, 8, 173, 62, 168, 49, 216, 64, 65, 116, 188, 106, 120, 199, 208, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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